readme: tighten cost claim and agent copy#144
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe README text is updated: the top-line performance claim now reads "Cut agent token costs by ~40% in benchmarks," and the .graph agent-consumption phrasing is changed to "native search & file reading tools." No behavioral or API changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 56 minutes and 11 seconds.Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 3: The headline "Save 40%+ on agent token costs with code graphs." is an
over‑general claim; update that copy (the exact string "Save 40%+ on agent token
costs with code graphs.") to qualify the savings—e.g., append "in our
benchmarks," "in tested scenarios," or "up to 40%+ in benchmarked workloads"
and/or add a parenthetical or footnote linking to the benchmark methodology so
readers don’t treat it as a universal guarantee.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
- "up to 40%" → "40%+" (more direct) - "normal file-reading tools" → "native search & file reading tools" (more precise)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
527b4e0 to
7b1d898
Compare
Summary
No code changes.
Summary by CodeRabbit